Navigation system for a 3D virtual scene

ABSTRACT

A navigation system for navigating a three-dimensional (3D) scene that includes a model or object with which a user can interact. The system accommodates and helps both novice and advanced users. To do this, the system provides the capability of tapping a hotkey to activate and deactivate tools.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is related to and claims priority to U.S. provisional application entitled Steering Wheels having Ser. No. 60/975,366, by Fitzmaurice, et al, filed Sep. 26, 2007 and incorporated by reference herein. This application is also related to and claims priority to U.S. provisional application entitled Steering Wheels having Ser. No. 61/022,640, by Fitzmaurice, et al, filed Jan. 22, 2008 and incorporated by reference herein.

BACKGROUND

1. Field

The embodiments discussed herein are directed to providing the capability of tapping a hotkey to activate and deactivate tools.

2. Description of the Related Art

Today, operating with three dimensional (3D) scenes is becoming more and more common. As a result, new or novice users are being confronted with a system that can be difficult and hard to use. However, it is also necessary to allow experienced users to also use the 3D systems effectively. What is needed is a system that accommodates and helps both novice and advanced users.

SUMMARY

A navigation system for navigating a three-dimensional (3D) scene that includes a model or object with which a user can interact. The system accommodates and helps both novice and advanced users. To do this, the system provides the capability of tapping a hotkey to activate and deactivate tools by detecting activation of a trigger key, determining whether to activate, deactivate or keep active a tool responsive to trigger key activation while no mouse buttons are pressed.

These together with other aspects and advantages which will be subsequently apparent, reside in the details of construction and operation as more fully hereinafter described and claimed, reference being had to the accompanying drawings forming a part hereof, wherein like numerals refer to like parts throughout.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates view object, tour and full navigation GUI wheels and the corresponding mini or pie cursor GUIs.

FIG. 2 depicts a 2D wheel.

FIG. 2a depicts other mini-wheels.

FIGS. 3a and 3b depict the hit zones of the wheels.

FIG. 4 shows cursor motion and wedge tool focus.

FIGS. 4a and 4b shows switching between big and mini wheels.

FIGS. 5A-5D show pie cursor operation.

FIG. 6 shows enlarged hit zones for the pie cursor.

FIG. 7 shows cursors to various tools.

FIG. 8 shows cursor wrapping.

FIG. 9 shows tool tips.

FIG. 10 illustrates close too and open tool menu nibs.

FIGS. 11a-11d show first contact GUIs.

FIG. 12 shows a cursor when used in a model point zoom with the center tool.

FIGS. 13-15 show center point section and centering.

FIGS. 16-18 show the focus sphere characteristics.

FIG. 19 shows locations of a sphere relative to a model.

FIG. 20 shows an orientation ring.

FIGS. 21 and 22 show tool warnings.

FIGS. 23a-23c show rewind cursor appearance.

FIGS. 24a-24c show rewinding.

FIG. 25 shows a forward tool tip.

FIG. 26 shows a warning for an invalid action.

FIGS. 27a and 27b show a perspective slider.

FIG. 28 shows forward motion.

FIG. 29a shows an up/down slider and 29 b shows up down motion.

FIGS. 30-32 show a walk.

FIG. 33 shows walk cursors.

34A, 34B and 34C show optional cursors for the mini wheel or pie cursor.

FIG. 35 shows tap activation operation.

FIG. 36 shows center operation.

FIG. 37 shows sphere operation.

FIG. 38 shows cursor wrapping operation.

FIG. 39 shows zoom operation.

FIGS. 40 and 41 show rewind operation while FIG. 40a shows the history data structure.

FIG. 42 shows forward operation.

FIG. 43 shows up/down operation.

FIG. 44 shows walk operation.

FIG. 45 shows pan operation.

FIG. 46 shows mini-wheel activation operation.

FIG. 47 shows parity maintenance between perspective and orthographic projections.

FIG. 48 shows system hardware.

DETAILED DESCRIPTION OF THE EMBODIMENTS

The embodiments of the present invention discussed herein provide a navigation system for three dimensional (3D) scene navigation for new and experienced users that allow fast and safe navigation within a 3D scene (or 2D scene). The system, as depicted in FIG. 1, includes a set 100 of graphical user interface (GUI) navigation widgets or wheels (or navigation tools) and corresponding miniature or pie menu versions, action tools that can be activated with the widgets and accompanying GUI navigation aids (not shown in this figure). The tools allow the user to perform different operations within the scene, such as panning and zooming.

The set of widgets or wheels, as includes a view object wheel 110 would typically be used by a novice or an inexperienced 3D user to navigate around an object in a scene, such as a model of an automobile or a part. The view object wheel 110 includes a center action tool 112. The center tool 112 is located in the upper wedge of the view object wheel 110. The center tool is designed to bring (through an automatic pan operation) a clicked point on a model part or other object to the center of the canvas view. A tool 110 secondary purpose is to establish a reference point in 3D space for other tools on the wheel 110. The orbit tool 114 allows a user to orbit around an object in a scene where the center of the orbit is the center reference point. The zoom tool 116 allows a user to zoom in toward or out away from the center point. The rewind tool 118 allows the user to rewind back through way points that are automatically saved as the user navigates about a scene.

A tour wheel 120 would typically be used by a novice to navigate within a building. A full navigation wheel 130 is designed for an experienced user and includes all of the tools of the object 110 and tour 120 wheels. The tour wheel 120 includes the rewind tool discussed above. The tour wheel 120 also includes a forward action tool 122. This forward tool 122 allows a user to move forward in the scene toward an object or model in the scene. If there is no object beneath the cursor, no motion occurs and the user is informed that no motion will occur via an invalid action or prohibited action message. A look tool 124 allows a user to “look” or change the view toward the left, right, up or down much the way a person turns their head in these directions. An up/down tool 126 allows the user to move vertically up and down within the scene.

The full navigation wheel 130 includes all of the tools functionality of the object 110 and tour 120 navigation tools with additional capability. A walk tool 132 allows users to interactively walk about in 3D space, moving forward and backwards and/or turning freely to the left or right. A pan tool 134 allows the user to move up, down, right and left in the scene. The zoom tool moves in and out from the current cursor position instead of the center point.

Each of the wheels 110, 120 and 130 has a corresponding miniature or mini wheel 142, 144 and 146, respectively, each of which includes the same action tools arranged in a pie type shape with each action tool occupying a pie wedge that corresponds to the general location of the action tool in the full size version.

A 2D navigation wheel 150 can also be provided as depicted in FIG. 2 and includes the zoom 152, pan 154 and rewind 156 tools.

FIG. 2a depicts enlarged versions of different mini-wheels some of which have places for additional functions.

The navigation tools or wheels have some common characteristics.

The wheels are all tracking menus. A tracking menu is a cluster of graphical buttons, as with traditional menus, the cursor (sometimes shaped like an arrow) can be moved within the menu to select and interact with items. However, unlike traditional menus, when the cursor hits the edge of the menu, the menu moves to continue tracking the cursor. Thus the menu always stays under the cursor and close at hand. Each wheel is displayed on the “canvas” of the screen display for 2D drawing and 3D model views. As long as the tool is active the wheel's menu surface will track and follow the mouse or input device cursor when it hits the edge of the menu surface. No mouse button down is required to get the menu to follow along. If the mouse cursor leaves the canvas area, the menu still follows the mouse off-canvas, and the navigation tool menu will re-display when the mouse cursor returns to the canvas and moves the menu along with it.

Each wheel is “pinned” to the mouse cursor when the left mouse button is held and a child tool is selected. When a child tool is no longer in use, the wheel re-appears under the mouse cursor on the canvas. The cursor is displayed exactly on the tool where it clicked to start the tool usage. So, for example, when the zoom tool is released, the wheel is aligned under the cursor exactly as it was when the mouse button was first pressed, while the cursor was on the zoom tool. This allows users to quickly re-invoke the same tool if needed. If the mouse cursor is off the canvas when the sub-tool is exited, the wheel continues to track the cursor. If the user moves the cursor back towards the canvas area the wheel is moved along until it becomes visible again.

Each of the wheels has the most used functions or action tools on an exterior and lesser used functions in the center. In addition, functions can occupy different amounts or space consistent with the importance of that function. The wheels, both full and mini, can have different sizes from 256×256 pixels down to 16×16 pixels. At a size of 32×32 the arrow cursor is no longer visible. The wheels appear on top of the canvas and any objects that are in the canvas are still visible since the wheels can be made semi-transparent. The wheels' level of opacity can be set in a range between 25% and 90% (i.e., mostly opaque). No matter what the transparency setting, the navigate tool or wheel is completely hidden (invisible) while one of its child tools is in use. Each child tool will determine any on screen display that may be required for itself. When the child tool is released, the wheel is redisplayed using the current transparency settings.

The area of each action tool is highlighted (including wedges in the mini wheels) as the cursor moves over the tool to alert the user that the user is over that tool. The area of each tool corresponds to the activation or hit zones, as depicted in FIGS. 3a (big wheels) and 3 b (mini wheels), unless the area is enlarged or enhanced, as will be discussed in more detail later. As a cursor is moved about on the menu, the cursor location is mapped to a corresponding location in representation of the hit zones. If the cursor is in one of the zones, that tool is highlighted. If the left mouse button is clicked down or activated while in a zone the tool corresponding to the zone is activated and the function starts at the point of the cursors.

The highlighting and selection for a mini wheel is particularly depicted in FIGS. 4 and 5. With the mini wheel, a full size wheel is miniaturized into a cursor-size with a radial layout based on the particular corresponding full size navigation tool selected and in effect becomes a pie menu cursor. The cursor (arrow) is preferably hidden and, in effect, the mini wheel menu itself serves to show cursor location. When the hidden system cursor hits the edge of the mini wheel, the mini wheel follows the system cursor. However, depending on which direction the mouse is moved, the command in that direction within the pie layout is highlighted as depicted in FIG. 4. Preferably, command or tool wedges are color-coded with one wedge active at all times and a small label is shown below the cursor to indicate the tool name as shown in FIG. 4.

A mouse down event activates a highlighted command and the mini wheel cursor is replaced by the appropriate tool cursor. A user can then drag to operate the command (for example, dragging to zoom in/out using the standard zoom tool cursor). Releasing the mouse button brings back the mini wheel cursor as depicted in FIGS. 4a and 4 b. The selection and operation of any of the commands in a mini wheel cursor is only one button press away and can be performed in-place. The one button press indicates both which command is being activated and the starting point for that command. By strategically planning ahead, a user is able to adjust their mouse input “approach path” to select a target object such that the desired command wedge is highlighted when over the target object. Thus, the desired command can immediately be activated with a mouse down event. This effectively merges pointing and command selection into a single act.

FIG. 5, including 5 a-5 c, shows an example usage of pointing, command selection and command operation for the mini wheel cursor. FIG. 5a shows the cursor motion to highlight a command. FIG. 5b shows clicking to activate the command (a pan tool). FIG. 5c shows dragging to operate the pan tool and FIG. 5d shows the release of the mouse button to deselect the tool and restore the mini wheel cursor.

The wedge selection or tool associated with a mini wheel or pie cursor can be enhanced by extending the hit zone of the active wedge as shown in FIG. 6. As depicted the wedge hit zone is expanded (dotted line) to be larger than the visible tool wedge by a small percentage such as 10%. This allows for a subtle form of wedge stickiness and also serves to reduce the instability that can occur if the input point is at the center of the pie cursor. The hotspot for the pie cursor lies within the active wedge and is the true cursor position. Since the wedges are fairly small, and the true cursor position is usually at the outer edge of the wedge, the hotspot becomes very predictable. As previously discussed, the pie cursor is not a pop-up menu; rather, like a regular tool, you select it from the toolbar and it becomes your cursor thus changing your input mode.

Each wheel exhibits a slide under behavior when the ShowMotion UI and/or the View Cube are displayed on the canvas. The wheel passes under both of these other features' onscreen displays.

FIG. 7 depicts cursors that can be used when the look 702, pan 704, orbit 706, zoom 708, rewind 710 cursors are activated, as well as the prohibited operation/action cursor 712. Each of the cursors has text associated with it when it is displayed above the canvas that provides the name of the tool, such as the “Orbit Cursor” text shown for the orbit tool cursor 706.

As the above cursors are moved about on the canvas, when the cursor encounters the edge of the display or canvas, the cursor wraps around as depicted in FIG. 8. As can be seen as the cursor moves from position 1 to 2 to the left edge of the screen, the cursor reappears on the right side of the screen at the same vertical position and traveling in the same direction as shown by positions 3 and 4. When the cursor exits the top or bottom, the cursor reenters at the same horizontal position.

All of the tools of each wheel can have a tool tip or description graphic (HUD—heads-up-display) that is displayed when the cursor hovers over the tool. FIG. 9 depicts a tool tip 902 for the pan tool 904 and a tool tip 906 for the orbit tool 908. The tool tips are the same size for each function. The HUD may also be shown below the cursor while a tool is in use. This HUD display element can follow the cursor about on the canvas while the tool is active (left mouse down) and is removed when the user exits the tool (left mouse up). Some tools may offer more complicated displays or aids than just a description.

As depicted in FIG. 5, each full size wheel 1000 has a close button 1002 that closes the GUI. The system stores and will remember the last tool that was in use when one of the wheels is activated. When a wheel is closed or dismissed, the previously active toolbar tool is restored or made active. If no other tool has been activated in the session, the “Select Tool” menu will be activated by default when closing a wheel via the close button. Each wheel also includes a menu button 1004. When the menu button 1004 is left mouse clicked, a menu is displayed. Right mouse click anywhere on the wheel surface will also display this menu. As with standard menus, hitting the ESC key will cancel the menu. The menu items for the view and tour wheels can include:

Mini View Object Wheel Mini Tour Building Wheel Mini Full Navigation Wheel ----------------------------- Full Navigation Wheel Basic Wheels  -> View Object Wheel Tour Building Wheel ---------------------------- Go Home Fit to Window Restore Original Center ---------------------------- [Application specific menu items, if any, go here] ---------------------------- Help... Preferences... ---------------------------- Close Wheel

The menu items for the full wheel can include:

Mini View Object Wheel Mini Tour Building Wheel Mini Full Navigation Wheel ----------------------------- Full Navigation Wheel Basic Wheels  -> View Object Wheel Tour Building Wheel ---------------------------- Go Home Fit to Window ---------------------------- Restore Original Center Level Camera Increase Walk Speed Decrease Walk Speed ---------------------------- [Application specific menu items, if any, go here] ---------------------------- Help... Preferences... ---------------------------- Close Wheel

When the 2D wheel is active it will display the following menu items in its menu:

Go Home Fit to Window ---------------------------- Help... Preferences... ---------------------------- Close Wheel

The first four menu items in the view, tour and full wheels switch to the corresponding wheel, the “Basic Wheels” is a sub-menu with the two novice wheels. Go Home moves the camera to the document's saved Home View with a quick animation lasting 1 second. Fit to Window adjusts the current camera to frame the 3D content to fit entirely within the view. Level Camera flattens the camera view rotation relative to the XY ground plane. Restore Original Center restores the view object wheel center point to the center of the currently loaded model's bounding box. Increase/Decrease Walk Speed doubles or halves the current walk speed. Help brings up the help window for the wheels. Preferences brings up the Preference window for the wheels. Close Wheel exits from the current wheel navigation tool and returns to the previous tool (or the default tool such as Select). Optional wheel menu arrangements can be provided.

To help users get started a set of graphic tool tips is provided that includes first contact tool tips depicted in FIGS. 11a and 11b for those new to 3D navigation and those familiar with 3D navigation. FIG. 11a shows an initial graphic 1100 that includes tabs 1102 for novice and advanced users. The tab for an advanced user is shown as selected includes a graphic 1104 of a full navigation wheel, the mini wheels and a tip 1106. The tip 1106 provides text on behavior 1108 (tracking and hide/show wheel) and wheel type selections 1110. The user can see each selection type by positioning the cursor over a type. FIG. 11b illustrates a display of the full mini wheel type tip where all of the tools and their locations on the mini wheel are shown. In FIG. 11b the full navigation wheel tool tips has been selected for review and the locations and of the actions/names of tools are noted. FIG. 11c illustrates possible selections within the novice tab and once again text describing behavior and possible selections are shown. FIG. 11d shows a view object wheel tip having been selected where the operations of the tools for that wheel are described in text. The typical use is show by an image 1112 along side the other tool 1114.

When the system is first run and a 3D model is loaded into the canvas either the view object wheel or the full navigation wheel is preferably be displayed in the canvas or display in the lower left corner. While displayed in this manner the wheel is even more transparent than when it is active. The wheel is in an inactive or pinned state, and only responds to mouse cursor rollover. While in this state the pinned wheel does not interact with any other tools or features. The pinned wheel has no other functions. After the first run from installation, the currently selected wheel is pinned to the same location. (The wheel selection is stored as an option across sessions.) If a mini wheel is the currently selected wheel, then the full navigation wheel is displayed. When the user moves the cursor into the pinned wheel's space a small combined graphical tooltip as discussed above and roll-over switch will pop up. As described above, the tool tip is broken up into different regions corresponding to a wheel type. When the cursor rolls over one of these tooltip regions, the pinned wheel changes to bring up the matching wheel. When a mouse click is detected in the tool tip region or the wheel, the current wheel is activated (i.e., unpinned). The wheel is not to be pinned on startup again unless the user goes and re-enables the behavior manually (“Always Show the Pinned Wheel on Startup” setting). If no click is detected the wheel stays pinned on cursor exit. If the user does not click and moves the cursor beyond either the border of the wheel or tool tip, the tool tips go away and the wheel remains in the pinned state. Preferably, to get rid of the wheel users first activate it and then close the wheel, or select another tool. Otherwise the wheel remains pinned in the 3D canvas.

A main menu pull down menu can also be provided in an application to allow activation of one of the navigation tools, such as:

Mini View Object Wheel Mini Tour Building Wheel Mini Full Navigation Wheel ----------------------------- Full Navigation Wheel Basic Wheels  -> View Object Wheel Tour Building Wheel

Where the above-menu is ordered for an advanced user and could be inverted in order for a novice user.

As previously mentioned the center tool moves a clicked or designated point on a model part to the center of the view and establishes a 3D space reference point. When the user places the cursor over the center wedge and over a model part in the canvas or scene at the same time, the cursor will display as the select arrow 1202, as shown in FIG. 12. When the user left mouse clicks to use the center tool, and starts to drag, the cursor icon changes to show the prohibited/invalid operation or action cursor/symbol (see FIG. 7) as long as there is no model part directly under the cursor. A HUD message will also be displayed with the text “Click or Drag over the model to set the Pivot.” When the cursor is over the model a center sphere, which will be discussed in more detail below, is displayed. The center sphere will not move with the cursor as long as the cursor shows the prohibited symbol. When the cursor rolls or moves over a model part the sphere jumps to that position and begins to track the cursor, and the icon will change to the normal arrow icon. The HUD message will then also go away. If the cursor is over the center wedge but not over a model surface, the left mouse click will display a momentary HUD message until the mouse-up event occurs that has text as noted above. If the Center Tool is active and the cursor is over a model part, then the system shows the center point sphere at the cursor's location in screen space projected onto the underlying model's surface as depicted in FIG. 13 (circled for ease of identification). Upon mouse up the view will be animated/panned to bring the current center point to the center of the canvas or view as shown by the arrow in FIG. 14 where the “ghosting” is used to illustrate this movement. When the center point reaches the center of the canvas the automatic view pan operation stops as shown in FIG. 15 and the center point sphere can be hidden. The center point is stored for use with other tools on the view object wheel to use, namely zoom and orbit. While the center tool is active, a graphical tool description is shown below the cursor location on the canvas with the following text: Center Tool.

The center point sphere represents a 3D point in model space. As discussed above, this point is set by the center tool and used by the orbit and zoom tools that are found on the view object wheel. If the user has not defined a center point by clicking in the canvas view, then the default center point location in space is preferably defined as the center of the currently loaded Model's bounding box. The sphere is a 3D model that is placed into the current model view. Since the sphere is a geometric object with 3D geometry it may appear larger or smaller depending on how far the target point is from the camera view, and it may be occluded by any model geometry that falls between it and the camera view.

Preferably, the center sphere is a “green ball” pivot indicator 1602 preferably with a text label 1604. The sphere can have axis rings 1702 around the perimeter as depicted in FIG. 17. The sphere should always be visible and should be displayed completely solid when there is no intervening geometry, and be displayed as partially see through when there is occluding geometry between the camera and the sphere as depicted in FIG. 18 where the sphere is shown with the label “Pivot” from the orbit tool. Note that as the two planes occlude the sphere the sphere becomes see through and remains visible. FIG. 18 shows a view with a corner of a cube pointing out of the page with the top 1802 of the sphere above the cube and the reminder of the sphere inside the cube. FIG. 19 illustrates a sphere completely outside a model (19 a), completely inside the model (19 b) and embedded in the model (19 c).

The sphere is preferably always accompanied by a text label where the label appears in a fixed pixel size on the canvas. The label is preferably always drawn in front of any model geometry in the view. The label text changes depending on which tool is using the center point sphere. The label text when seen with the center tool is: CENTER

The view object wheel version of the orbit tool 114 (see FIG. 1) or command preferably always gets its pivot point from the center tool center sphere. It is preferably placed on the wheel at the bottom three quadrants. It also maintains a dominant up-axis of the scene or canvas. A left mouse click anywhere in the orbit wedge hit zone invokes the orbit tool. For the view object wheel the last defined center point (from the center tool) is used as the orbit operation's pivot point. Horizontal and vertical mouse movement rotates the view about this pivot point in the same way as the standard orbit tool does dragging the cursor on the canvas to the left orbits the camera view around the pivot point along the world Y axis and moves the camera to the left, the model appears to turn to its right. Drag to the right does the opposite. Dragging the cursor upward orbits the camera around the pivot point on the X axis relative to the screen and moves the camera downward. Dragging the cursor down does the opposite. While the mouse is held down and the orbit tool is active the cursor is changed to the orbit cursor 706 (see FIG. 7). The cursor is allowed to wrap around the canvas when the Orbit tool is active. When the orbit tool is active the center point sphere is preferably displayed in the canvas and the sphere's text label is shown: CENTER. By default the system maintains the scene upright with respect to the model. If this default is off, the orbit tool behaves in screen space (not model space). When “Keep Scene Upright” is turned off, the orbit algorithm is changed to not force an explicit up direction. When “Keep Scene Upright” is off, a shift key modifier can be enabled that, on mouse-down presents a graphical roll ring 2002 (see FIG. 20) HUD centered around the current pivot point, where up/down mouse motion adjusts the roll values for the camera. Note that the label for the green ball pivot point is turned off while the roll ring 2002 is up. When a user makes a selection using the orbit tool, the pivot or center point is moved to the center of the bounding box of the current selection. Subsequent orbit operations will use this pivot point unless it is moved again by another selection or other navigation actions (e.g., Pan operation, etc.).

The zoom tool 116 (see FIG. 1) is invoked by clicking while in the hit zones for the tools on the wheels 110 and 130. The typical zoom-in and zoom-out operations preferably occur relative to the center point set by the center tool. However, the zoom for the view object wheel has some constraints placed on it that are not found in the version that is provided for the full navigation wheel. The view version of zoom tool is constrained in the following by the system so that it cannot zoom (dolly) in further than its focus point, it cannot zoom out farther than the minimum size constraint, and it can only zoom directly in to the center of the canvas, as it uses the target point set by the center tool as its focus. In the view object wheel the zoom tool is preferably placed in the top of the center two wedges just above the rewind command. The zoom tool has a graphical tooltip that includes the text: Zoom in or out from Center. Whenever the zoom tool is active, the target point is indicated in the HUD by the green center point sphere with a text label: CENTER. When the camera is zooming, either automatically from a single click zoom, or interactively with the click and drag zoom, the zoom cursor previously discussed is shown along with the zoom custom HUD with the text “Zoom Tool” below the cursor.

During operation, after a single left mouse click and release the camera view will perform an animated transition and zoom in towards the current target point. The amount the camera travels during this transition is preferably defined as 25% of the distance from the camera view's current location to the target point location. The zoom tool on the view object wheel preferably always uses as its target point the last point created by the center tool. This means that the view object wheel zoom tool preferably always zooms directly to the center of the canvas. Zoom is typically a camera dolly operation; it typically does not change the camera's field of view (FOV) in any way. Holding the Shift key when clicking the zoom tool inverts the single click zoom, and moves the camera view directly away from the target point. The zoom out distance is preferably defined as 125% of the distance from the current camera view location to the target point location.

Clicking on the zoom tool wedge will activate the zoom tool and also allow mouse dragging to zoom in our out from the current focus point. Again, the last defined center point is used as the target point for the view object wheel zoom tool. This means that this version of zoom always zooms in to the center of the canvas.

In the view object wheel, the zoom tool cannot zoom in forward beyond the target point. The camera view will stop moving once it reaches the Target Point and further mouse drag in that direction will have no effect. The user can always reverse mouse drag direction to zoom back away from the Target Point. When the user has reached this boundary an additional message is displayed in the HUD: Change the Center point to zoom further

The zoom tool is also constrained when zooming out or away from the target point when using the view object wheel. The camera view cannot be moved further away than a maximum distance, which is determined by the model's bounds. Once the view has backed out to this maximum distance the camera will stop and further mouse drag in that direction will have no effect. User can always reverse their mouse drag direction to zoom back inward. A HUD message is provided as depicted in FIG. 21 with this figure indicating 2102 a maximum zoom-out has been reached. When the user has reached this boundary an additional message can be displayed in the HUD as depicted in FIG. 22. Also FIG. 22 shows that the HUD message is readable on a variety of background colors since it is always drawn with white text on a semi-transparent grey box.

The zoom tool can have additional modes available. When tool is active and the user holds down the Shift key, a “+” cursor is shown and the system allows the user to perform a “zoom extents” operation. In this operation, clicking and dragging define a rectangle which is visually shown to the user, to define a zoomed view. Releasing the mouse after the clicking and dragging, zooms the view (using an animation) to match the defined rectangle as best as possible. At the end of the transition, the visual zoom rectangle fades away.

A cursor drag up or drag right will zoom the view in. A cursor drag left or drag down mouse will zoom the view out. By default the directions for zoom-In are cursor drag up and right, but this can be inverted based on the zoom direction options dialog setting.

The mouse scroll wheel can also be enabled for the view object wheel. Scrolling the wheel forward causes the view to zoom, and backwards to zoom out. Zooming with the scroll wheel is preferably always towards, or away from, the center of the canvas. While scrolling with the wheel the target point sphere is displayed at the center of the canvas with the label discussed previously.

The rewind tool is found in all of the wheel interfaces. Its behavior does not change no matter which wheel it is found on. It is located in a wheel differently depending on the wheel. The tool allows the user to navigate 3D spaces with a level of security as they can always rewind back through their navigation history to a previous view location. The tool presents this rewind history as a set of onscreen thumbnails that show each step the user has so far taken so far. The rewind tool also lets users interactively drag between the waypoint thumbnails to run back and forth through their navigation history animating the camera view as they do so. When the cursor is held over the rewind tool a tooltip is shown below the wheel in the canvas with the text: Rewind through your movement history. The system uses “waypoints” to facilitate the rewind function or command. Each waypoint is a captured camera view position+orientation, along with a thumbnail of the model as seen from the camera's current view at that location. As the user navigates using: the tools provided by the wheels (e.g., forward, orbit, center), or the ViewCube available from AutoDesk (clicking or dragging) or any other 3D scene navigation tool, these events are added to the navigation Rewind history. Every camera and viewport combination has a separate Rewind navigation history queue. Thus, in a quad view (2×2 viewport) arrangement where there is a Front, Top, Right and Perspective camera/view, 4 separate Rewind queues are maintained. Each time the mouse is released when using a navigation tool; the system stores the current view as a new waypoint and appends it to a history list for that camera/view combination. This new waypoint is set as the “current” waypoint. In general, waypoints are preferably not captured or recorded (but can be) at stages during a tools usage, only at the ending view position when the tool interaction is completed. Some tools, such as the walk tool described below, can generate multiple waypoints (see section below).

FIG. 23a illustrates a cursor positioned over the rewind tool in the view navigation widget, when the user clicks on the tool, the widget fades-out and the waypoint history fades-in as shown in FIGS. 23b and 23 c.

The rewind history list preferably works like an Undo/Redo mechanism, when the user rewinds and subsequently creates a new waypoint the new waypoint becomes the end of the history list and all others after it in time are discarded. The rewind history is stored for the current model only. If a new section or model is loaded then the history is discarded. The rewind history also persists across wheel switching and all of the wheels can make use of it in the same manner. When another tool is selected and the wheels are dismissed, the rewind history continues to be stored. When the user returns to navigation with the wheels by selecting them again, all previous history waypoints are retained and the user can rewind through them normally. A maximum number of history events are saved (by default 100 events).

A single mouse click on the rewind wedge in the wheels 110, 120 and 130 (see FIG. 1) will temporarily activate the rewind tool and display the history waypoint thumbnails as discussed above. Upon releasing the mouse the rewind history is backed up to the previous waypoint in the list. That previous waypoint is set as the “current” waypoint. The wheel is redisplayed and an animated camera transition is performed to transition the current view to the older waypoint's location and orientation. The rewind history thumbnail strip is displayed during the rewind animation. If no history has been created yet and the user clicks the rewind tool, the system displays an empty rewind thumbnail and does not change the camera view in any way. The arrow cursor is hidden and the cursor for the rewind tool, called the timeline or rewind cursor and composed of four corner brackets as shown in FIG. 24 a, is displayed while the mouse is held down. While the mouse is clicked or held down the rewind tool graphical tool description element (HUD) is displayed below the cursor on the canvas with the text: Rewind Tool. Note that this HUD element will appear in front of the thumbnails.

If the user left mouse clicks and holds the mouse down, the rewind GUI as shown in FIG. 24a is displayed. This GUI is a set of thumbnails 2402 arranged in a row horizontally in the canvas over objects of the scene. The most recent or current history waypoint's thumbnail 2404 is shown directly under the rewind cursor 2404 (angle lines around the thumbnail) and centered (vertical and horizontal) on the cursor position. Older waypoint thumbnails are shown to the left and will be clipped by the canvas edge if there are too many to display. Newer waypoints are shown to the right and also may be clipped by the canvas edge. (Clipping simply means these are HUD elements and will not be draw outside the canvas bounds.)

If the user then drags the cursor to the right or left the current waypoint's border will start to fade out and the next (in the dragged direction) thumbnail's border will begin to brighten as shown in FIG. 24 b. The border is brightest when the cursor is dead center horizontally on a given thumbnail.

The distance the cursor is currently placed between any two waypoint thumbnails is used to control the transition of the camera view between those two waypoint locations and orientations. So, if the cursor is halfway between two waypoints, the camera view will be smoothly animated to the halfway point between the two waypoint view locations using linear interpolation. The camera view is constantly updated to follow the transitions between these thumbnails and waypoints as the user drags over them using the linear interpolation. This sequence of cursor position changes and corresponding scene changes is shown in FIGS. 24a -24 c. Note that additional positional hints (instead or in combination with linear interpolation) may be used to more accurately reproduce the motion history. A noticeable snapping occurs when the cursor is dragged near the center of a thumbnail to allow a user to match exactly the saved waypoint view.

When the user releases the mouse the camera will remain at its current position and orientation even if this is part way between two waypoints.

When the mouse is released: If the closest thumbnail under the cursor is not the last in the history list (there are more thumbnails to the right of it) or the cursor is not exactly on a saved waypoint, a new waypoint thumbnail will be generated and info will be stored or updated. This selected waypoint becomes the “current waypoint” and any new waypoints will be created after it in the list. If there are any new waypoints created, the entire list from this current one on will be discarded.

When the mouse is released if the closest waypoint under the cursor is the last waypoint in the history list (no more thumbs to the right of the selected item) then the waypoint's information is replaced with the camera's current position+orientation+thumbnail. This last waypoint becomes the current waypoint and any new views will be created after it in the list.

The rewind cursor is constrained to move only horizontally and graphical “corner borders” are also displayed surrounding the cursor to frame the current thumbnail.

To access rewind history beyond what is currently visible in the thumbnail strip on the canvas, an automatic thumbnail strip scrolling has been defined. When there are only two visible thumbnails remain in the history due to canvas clipping, the rewind cursor remains fixed and the thumbnail strip begins to move in the opposite direction of the mouse movement. This movement is position-based not rate-controlled.

Rather than discard (or write over) all later in time waypoints when a past waypoint is selected, it is also possible to create a branch in the rewind history and maintain all of the waypoints. Multiple waypoints can also be compressed. As previously mentioned, waypoints are typically saved at the end of tool operation and at intervals within some tools. However, it is possible to constantly record waypoints in “high resolution” with small separations in time between them.

As previously discussed the tour building wheel 120 (see FIG. 1) is primarily focused towards moving the camera (user) about in 3D building models or virtual spaces. It allows for forward movement, looking about, and moving between vertical floors. Along with the common close and menu buttons, this wheel provides four tool wedges: forward, up/down, look and rewind. The rewind tool has been discussed above. Normally the middle mouse scroll wheel (hardware) is allowed to zoom the view in or out. While the tour wheel is active the zoom behavior of the middle mouse scroll wheel is disabled to prevent the user from escaping the constraints that are placed on 3D view navigation while using the tour wheel.

The forward tool or command is located at the top center of the tour building wheel 122 (see FIG. 1) occupying the top three quadrants of the outer ring and is the primary method for moving the camera for the tour wheel. The tool tip text 2502 for this tool is: “Click to set target. Drag to adjust distance to the target.” as shown in FIG. 25

The forward tool moves the view towards a clicked focus point location. When the mouse is clicked over a model surface with the forward tool, a focus point is defined by projecting the cursor location on the canvas onto the model surface using ray casting in a “click-through” type manner. If no model part falls under the cursor then camera view will not move forward and a prohibited operation cursor 2602 (see also 710 of FIG. 7) is temporarily displayed as shown in FIG. 26. If a model is found then the focus point is set, and the camera is animated moving (zooming) in towards the target point when the mouse is released. The total distance of this move is preferably half of the distance from the current view plane to the focus point. While animating the view forward, the wheel and the cursor are preferably hidden.

The center point sphere is reused as the target point and the sphere remains displayed until the user releases the mouse. For this tool the sphere has no label. Instead an endpoint 2702 of a perspective slider (HUD) 2704 reads: Surface—as depicted in FIG. 27 a. A mark 2706 is shown at the very bottom of the scale indicating the starting camera position. This marker is labeled with text: START. The distance indicator 2708 is displayed during the click to go forward camera transition. A distance marker 2708 moves along automatically with the camera motion. FIG. 27b shows the wiper or marker 2708 between the start position and the surface. The wiper changes size based on the drag distance (i.e., depth into the scene). This element is shown while dragging to set distance (also while the view is animating with the click to go forward behavior above.) This display element is placed into the view just below the cursor on the canvas. When the transition is complete and the camera stops moving, the distance indicator HUD is hidden. This graphical display gives feedback on the distance moved from the camera view's starting position towards the focus point. An optional set of dotted lines or pass through markers are shown above and below the target marker, these indicate that the user may go forward beyond the target (surface), or that they may back up past the start.

Clicking and dragging on the forward tool wedge also sets the focus point in the same manner as for the click to go forward behavior described previously, but instead of animating the camera towards the target automatically, the user may drag the mouse to move the view forward (and back) to set the distance to the focus point interactively.

Like with a zoom tool the user may perform both the forward and backward movement with a single mouse drag action. This is basically a zoom interaction but the zoom amount is capped in both directions. While interactively dragging the view with the forward tool, the tour building wheel is hidden. Dragging the mouse/cursor upward moves the view forward. Dragging the cursor downward does the opposite.

The zoom forward distance is capped so that when the user has moved (dragged) forward right up to the focus point position, the tool resists further mouse drag beyond that point in a resistance zone, which is a percentage of the distance to the surface, such as 95%. If the user continues to drag the mouse in the forward direction for a period of time, they will be allowed to “pop-through” the view to beyond the existing focus point position and continue to zoom in/move forward from there. This behavior allows users to push through solid surfaces or walls.

The user may also interactively move backwards from their starting position towards an invisible focus point that is behind the camera view. A “sticky point” or range of no movement is defined for the start position of the forward tool. To go backwards, the user must drag some distance downward to move off the sticky point. Similar to the forward movement, a ray is cast behind the camera view plane to try and see how far the user can move without entering a wall or passing through a model surface. If a surface is found, the camera is allowed to only move backwards as far as ½ the distance from the start position to the surface found behind the camera. Unlike forward the user cannot push beyond the surface that is detected behind the camera.) If no backward surface is found during the initial ray cast, the camera is allowed to move backwards a small amount (roughly 25% of a forward ray). Again the cursor is hidden during this behavior.

During use, a user places cursor over target and clicks on the forward tool wedge. At this point, as depicted in FIG. 28, a number things happen: the distance indicator HUD is shown just below the cursor's last location, the current position indicator is placed at the start position on the bottom of the vertical scale, the focus point sphere is shown in the model view and the arrow cursor goes away (see image 1 of FIG. 28). In this example, the user has clicked on the wall to the right of the fireplace. Next, the user can now drag the mouse to move forward (image 2), while doing so the camera is animated forward (zoom in) and the current position indicator or marker (having a color such as orange) moves up along the scale towards the “Surface” marker. (Note that the user can also drag to move backwards (zoom out) see details above.) When the user drags forward far enough to reach the focus point the forward view movement stops. The current position indicator aligns with the surface marker (image 3). If the user keeps moving forward, the movement resumes and they are allowed to pass beyond the surface and continue forward. The current position indicator continues to move upward past the surface marker. The focus point sphere will become more and more transparent as the camera view gets closer to it until it finally disappears and the camera view passes through it allowing the user to pass through the surface or wall (image 4).

The up/down tool 126 (see FIG. 1) is located in the bottom center wedge of the tour wheel and in the bottom right quadrant of the full navigation tool (130). The up/down tool gives users a way to move their view vertically between floors or levels of a building using an up vector in the model. Note that this is different than what is possible with the pan tool. Panning is dependent on the camera orientation. For example, if you are looking down at your feet (mostly looking at the floor) and then try to pan up to get to the next floor above you, this would take a long time and significantly displace you since you are sliding along the camera plane (screen space) which, when looking down, is at an angle with respect to the floor planes. The up/down tool slides along a Y-up axis of the scene without displacing the user along the horizontal plane of the view.

When the cursor is over the up/down tool on the wheel the tool tip text is: Move up or down.

A bounding box of the model (plus a small amount of extra padding 10-15%) is used to determine an absolute high and low Y axis values. The up/down tool is constrained by these values and cannot push the view beyond them in either direction.

To avoid sudden jumps in the camera view when the up/down tool is invoked the following rules apply. If the camera is already above the bounding box high mark when the user first clicks and drags the mouse, then the system uses the current camera position as the high mark. If the camera is already below the bounding box low mark when the user first clicks and drags the mouse, then the system uses the current camera position as the low mark.

When the up/down tool is active the display (see FIG. 29a ) shows a slider or scale 2902 that is similar to that of the forward tool display. This HUD is displayed centered vertically at the cursor's last position on the canvas, and vertically with the current position Indicator aligned the cursor's last location. The top 2904 of the scale is marked to show the highest point that the camera or view can be moved to with this tool. This point on the scale has a label: Top. The bottom 2906 of the scale is marked to show the lowest point that the camera can be moved to with this tool. This point on the scale has a label: Bottom. An indicator marker 2908 (preferably orange in color) shows the current camera view position relative to the High and Low positions. When the user moves the view up or down a slightly dimmer orange marker or shadow indicator 2910 is left in place to show the starting view position on the scale.

During use of the up/down tool, a vertical mouse/cursor drag upward (relative to the view) will push the view up towards the high or top marker. A mouse drag downward does the opposite. FIG. 29b shows an up and down motion. The drag amount of the mouse can vary the up/down camera direction directly or alternatively can move using a rate control design; this allows for small initial incremental camera movements and with more cursor dragging larger camera movements.

The look tool on the tour wheel has movement keyboard keys disabled whereas on the full navigation wheel, as discussed below they are enabled. The look tool 124 located in the top half of the middle circle on the tour building wheel 120 (see FIG. 1) and on the lower left quadrant of the inner circle of the full navigation tool 130 as will be discussed later herein. The tool tip when the cursor hovers over this tool reads: Look around your current position.

To look left or right, a horizontal drag or X-axis mouse movement (relative to the view) causes the view to rotate to the left or right. To look up or down, a vertical drag or Y-axis mouse movement causes the view to rotate up or down. The up and down looking is optionally constrained so that the view never flips upside down. The camera or view can be rotated until it looks nearly straight up or down in the tour wheel, but not beyond. When the Look tool is active the cursor is changed to the look cursor 702 as shown in FIG. 7. The cursor is allowed to wrap around the canvas when the look tool is active.

While the mouse is held down the look tool graphical tool description element is displayed below the cursor on the canvas with the text: Look Tool.

As previously discussed, the full navigation wheel 130 (see FIG. 1) contains eight tools: walk, up/down, look, center, orbit, zoom, rewind and pan.

The walk tool 132 allows users to interactively walk about in 3D space, moving forward and backwards and/or turning freely to the left or right. The walk is preferably along a horizontal axis or plane of the scene. The walk tool also allows shortcut key access to the up/down tool to adjust the view up or down while walking. The walk tool is preferably located in the top right interior wedge on the full navigation wheel. The tool tip text is: Click and drag in the direction you want to walk.

Clicking the left mouse button with the cursor over the walk tool activates the walk tool. When the mouse is first clicked on the walk tool the cursor changes to a default walk icon or cursor 3002 as depicted in FIG. 30. If the user moves the mouse even a tiny bit while holding the button down, the cursor is warped or moved to the center of the canvas (see arrow showing motion in FIG. 31), and a target circle or region or motionless zone 3102 is displayed. This actual position for this GUI display element (zone) is centered horizontally left to right and adjacent to the bottom about ⅓ up from the bottom of the canvas vertically. If the user further drags the cursor in any direction away from the center target 3102, then the camera view begins to move or “walk”.

The direction of the cursor from the center target or zone 3102 determines the walk direction. Up is forward, down is backwards, left is turn left, right is turn right, and diagonal combines the two closest headings. The distance of the cursor from the center target 3102 determines the speed of walking. The closer to the center is slower, farther away is faster. A default speed is set based on scene space parameters, such as the size of the bounding box, and can be changed by the user. Placing the cursor over the center circle area 3102 will stop camera or view movement. At any time the user may release the mouse button to end walking and redisplay the wheel.

While walking the cursor is changed to an arrow (a direction indication cursor) 3202 that indicates the current move direction and rotation. In FIG. 32 the diagonal arrow cursor 3202 indicates that the user is moving forward and turning to the left.

There is a default cursor 3302 for when the camera is not moving and the cursor is hovering inside the center circle or zone as shown on the far left of FIG. 33. There are eight walk direction cursors for when the cursor leaves the center circle HUD area as also shown in FIG. 25. These include forward 3304 and backward 3306, left 3308 and right 3310, and the four diagonals 3312, 3314, 3316, 3318 between the primary directions.

While the walk tool is active the following text is displayed as a HUD element on the canvas: Hold down Shift key to move up or down. This HUD text does not follow the cursor movement, and is instead fixed to the lower center of the canvas area.

While the walk tool is active the user may press and hold a hot key such as the Shift key at any time to temporarily activate the Up/Down tool and move up or down. The walk tool is suspended while the Shift key is held and the up/down tool is active and operates as previously discussed. When Shift is pressed the cursor location (and therefore the walking speed and heading) are temporarily stored. When the shift key is released the cursor is placed back to its previous location and the walk operation continues on from where it left off. A walk tool option allows users to adjust the walking movement direction based on their current camera looking direction instead of the default ground plane. Thus, it can be used in combination with the look tool to move around in 3D space.

It is possible and likely that users will activate the walk tool for long periods of time (30 seconds to a minute, etc). In order to capture some of these long walk events, the system defines multiple rewind events during a single mouse drag walk event. Preferably, this is the only tool that allows for multiple rewind events to be defined. By default, a walk rewind event is preferably recorded every 5 seconds. Consequently, a thumbnail is added to the rewind thumbnail strip (history) for each event. If it is not possible to create thumbnails during a walk (due to performance issues or if it is too noticeable during the walk), it may be possible to create the thumbnails on the mouseUp event or, a less favorable solution, to use the same thumbnail for all multiple walk events belonging to a given long walk drag history. To increase walk speed (increase movement rate) the user presses CTRL+Shift+>. To decrease walk speed (decrease movement rate) the user presses CTRL+Shift+<. Alternative hotkeys may be used.

The look tool 136 on the full navigation wheel 130 allows the user to move the view while looking by pressing the arrow keys on the keyboard. The tool is located on the bottom left interior wedge on the full navigation wheel 130 (see FIG. 1). The tool tip text is: “Look around your current position. Press arrow keys to move.” To look left or right, an horizontal drag or X-axis mouse movement in the view causes the view to rotate to the left or right and to look up or down, vertical drag or Y-axis mouse movement causes the view to rotate up or down (drag left allows you to look left; drag up to look up; etc.). This up and down looking in the full navigation tool is not constrained so that the view can flip upside down. The camera can be rotated continuously until the view somersaults.

The look tool can also have an additional mode. When the user holds down the Shift key while the tool is active, the system performs a “look at” operation. Similar to the Center tool, the green ball is positioned and can be dragged along the model surface. The surface beneath the green ball is highlighted. Once the key is released, the view animates to move the green ball to the center of the view, roughly keeping the zoom factor the same but orients the view to be looking “head-on” to the surface where the green ball resides (e.g., the surface normal is pointing directly at the user/camera).

Shortcut key inputs from the keyboard are provided to extend the look tool for users using the full navigation tool who have keyboard access. These keys will cause the camera to move forward or backward, and left or right. These movement commands are available while the look tool is active. (left mouse down). The forward key command causes the camera or view to move forwards (dolly in) based on the camera's current heading. For example, if the user is looking straight up and presses this key they will fly up into the air like superman. If they are looking straight ahead they will fly directly ahead. The camera movement rate for the keys is determined by a walk speed factor that can be set by the user. The move backwards key command causes the camera to move backwards (dolly out) based on the camera's current heading. The move left or sidestep left key command causes the camera to move to the left as if the user was panning horizontally. The move right or sidestep right key command causes the camera view to move to the right as if the user was panning horizontally. No up or down movement key is provided.

Both the walk tool and the look tool take into consideration the scales of the model space in which they are operating. The speed to move through an engine block is very different than what will work to move past the Empire State Building. A base movement rate value is automatically calculated, based on the model's bounding box when the model is loaded. Both look and walk use the same base setting. Increase or decrease speed commands can modify this base move rate setting to fit the user's needs, and these ± modifications can be stored for the duration of the session.

When the look tool is active the cursor is changed to the look cursor 702 as depicted in FIG. 7. The cursor is allowed to wrap around the canvas while the look tool is active. While the mouse is held down the look tool graphical tool description element is displayed below the cursor on the canvas with the text: Look Tool.

The orbit tool 114 appears on both the view object wheel 110 and the full navigation wheel 130. The version on the full wheel uses the same mouse control scheme to orbit the view about a pivot point, but this tool has a more dynamically defined pivot point that is not always directly in the center of the view. The tool is located on the left side wedge of the full wheel 130 (see FIG. 1). As other tools are used on the full navigation wheel, the pivot point location for the orbit tool is being constantly updated. By default the pivot is set to the center of the screen. The center point sphere 1602 (see FIG. 16) is preferably used for the pivot point. The sphere remains displayed until the user releases the mouse. For this tool the sphere label text is: PIVOT. While the mouse is held down and the orbit tool is active the cursor is changed to the orbit cursor 706 shown in FIG. 7. The cursor is allowed to wrap around the canvas while the orbit tool is active. While the mouse is held down the orbit tool HUD element is displayed below the cursor on the canvas with the text: Orbit Tool.

If the user activates CTRL+Click or CTRL+Click and drags on a model in the view with the orbit tool, a new pivot point is defined about which to orbit. Subsequent orbits will use this pivot until the user defines a new one by using another tool, such as zoom, another CTRL+click on the orbit tool and navigating the view with another tool so that the pivot location ends up off screen.

By default the Keep Scene Upright option is on. If it is turned off, then the orbit tool behaves in screen space (not model space). When “Keep Scene Upright” is off, a Shift key modifier is enabled that, on mouse-down presents a graphical ring HUD (see FIG. 20 previously discussed) centered around the current pivot point, where up/down or left/right mouse motion adjusts the roll values for the camera. The label for the green ball pivot point is turned off while the roll ring is up.

When a user makes a selection, the pivot point is moved to the center of the bounding box of the current selection. Subsequent orbit operations will use this point unless it is moved again by another selection or other navigation actions (e.g., pan operation, etc.).

Pan operation of the full wheel is preferably a common pan operation except that the clicked point in the view will stay fixed to the cursor and not go flying off too fast or too slow.

For the full navigation wheel the tool is not constrained, and can zoom towards or away from any point visible in the canvas. A single click to zoom in (left mouse button click and release) behaves like the single click behavior for the view wheel zoom tool, with the following exceptions. The target point is set based on where the user placed their cursor over the model, not the center of the canvas. The user is allowed to click anywhere on the canvas to set the zoom target point and zoom will zoom into this location. This behavior may be turned off. The single click to zoom out (Shift+left mouse button click and release) zooms out away from the clicked point on the canvas. The target point is set based on where the user placed their cursor over the model, not the center of the canvas. The user is allowed to click on ‘nothing’ and can still zoom. This Zoom tool also supports the invert mouse zoom option setting where the zoom can cause the scene to be inverted. Whenever the zoom tool is active on the full wheel, the target point is indicated as a green sphere with a text label and is the same HUD graphic as for the Center tool shown earlier. The mouse scroll wheel will zoom in to the last defined pivot/focus point in the same manner as the CTRL+Zoom shown above.

The mini wheels (see FIG. 1) are designed for advanced users and provide even more rapid access to the navigation action tools. Three Mini wheels exist which are task-based: mini view object wheel 142, mini tour building wheel 144 and mini full navigation wheel 146. The action tools within each mini wheel behave exactly like the big full wheel. The gestural and spatial location are similar to the big full navigation wheel. For example, orbit is on the outer left wedge in the big full wheel and the mini view object wheel. The mini wheels are preferably small (32×32 pixels) and replace the default “arrow” cursor. In this default small mode, the arrow cursor is turned off. The mini wheels can be made larger than the default 32×32 and in these cases, the arrow cursor is preferably made visible along with the active mini wheel. The mini view object wheel 142 contains the tools: zoom (top wedge), rewind, (right wedge), pan (bottom wedge), and orbit (left wedge). The mini tour building wheel 144 contains the tools: walk (top wedge), rewind (right wedge), up/down (bottom wedge), and look (left wedge). The mini full navigation wheel 146 contains the tools: zoom (top wedge), rewind (right wedge), pan (bottom wedge), orbit (left wedge), center (top-left wedge), walk (top-right wedge), up/down (bottom-right wedge), and look (bottom-left wedge).

Showing the standard arrow cursor within a mini wheel or pie cursor can be visually heavy and confusing. Preferably no cursor is shown and the mini wheel visually acts as the cursor. However, there may be times when it is useful to have a visible cursor. In such a situation, a smaller dot cursor (what can be called a flea cursor) can be provided as depicted in FIG. 34a or a miniaturized arrow cursor within the pie cursor that indicates the precise mouse input and active hotspot can also be provided as depicted in FIG. 34 b. A further alternative is to not show the mini wheel cursor but display a modified arrow cursor as depicted in FIG. 34 c. When the arrow cursor moves into a new command wedge of an invisible pie cursor, the visible cursor is changed to the corresponding tool cursor. Yet another approach is to use a click-hold design during command activation within the pie cursor to lock-in/release a command/tool mode. A velocity based alternative can serve as a means of switching between command selection (high velocity mouse movement) and precision pointing (low velocity mouse movement). To accommodate precision pointing, the user can hit a modifier key such as the Shift key which will lock-in the currently highlighted tool in the mini-wheel and replace the mini-wheel with an arrow cursor. Holding the Shift key will also retain the current tool for multiple mouse movements/clicks and allows the user to repeat a command multiple times until the Shift key is released and the mini-wheel returns

All of the wheels can share a particular key as a shortcut key. Pressing this shortcut can bring up the last used wheel for 3D, or just bring up the 2D wheel for 2D content. Tapping the shortcut key when a wheel is already up will bring the wheel down and activate the last tool (e.g., Select Tool). The CTRL+Shift or another key can be used as a shortcut key or hot key to activate/deactivate the wheels. Activating a wheel should occur “transparently” from the current tool. For example, if the a first tool is active, a user can hit Ctrl+Shift to activate the view object wheel, navigate, hit Ctrl+Shift again to bring down the wheel and be placed back into the first tool to continue working.

The flow of this shortcut key process 3500 is depicted in FIG. 35 and starts with the user activating (pressing) and the system detecting the trigger key 3502. The system then checks 3504 to determine whether the corresponding tool is active and, if so, when the user releases 3506 the key, the system checks 3508 to see whether the key was held down for at least a threshold amount of time, such as _1_ seconds. If held down for the threshold time, the tool is kept 3510 active, otherwise it is deactivated 3512. If the initial check 3504 indicates that the tool is not active, it is activated 3514. When the user releases 3516 the activation trigger, the system again checks 3518 the hold down time against the threshold, deactivates 3520 the tool when not met and keeps 3522 it active when met.

The center tool operation is depicted in FIG. 36 and starts with the user pressing the mouse button which is detected 3602. The system then checks 3604 to see if the cursor is over the model by ray casting the cursor into the scene and determining whether the ray encountered the model. If the cursor is over the model, the intersection point is determined 3606 and it is displayed 3608 on the model, preferably as the green ball. If the cursor is not over the model, the invalid operation message is displayed 3610. The system then determines 3612 whether the mouse button has been released and, if so, again checks 3614 to see if the cursor is over the model. If so, the model is moved or animated 3616 so that the intersection is in the center of the screen.

When the green ball or center sphere is used, it can be moved about in the model space. As depicted in FIG. 37, when the user presses 3702 a mouse button, the system checks 3704 to see if the cursor is over the model. If so, like described above, the intersection point is determined 3706 and the sphere is displayed 3708 at the intersection point of the model. If not, the system checks 3710 as to whether the active tool allows the sphere to be anywhere in the model space. If so, the sphere is displayed 3712 at a specified depth into the model from the current view position, such as the depth position from the last time it was on the model. If the sphere is currently displayed 3714 on the model, the sphere is not moved 3716 and, if not, the sphere is not displayed 3718. The button status is then checked 3720 and if it is not down, the sphere is not displayed 3722.

The orbit operation, except as described above, has a conventional flow and so is not described herein.

For the tools that allow cursor wrapping, this operation, as depicted in FIG. 38 starts with the user moving 3802 the input device for moving the cursor and this being detected. When the cursor x position is greater than the window width 3804, the x position is set 3806 to zero. When the cursor x position is less than zero 3808, the x position is set 3810 to the window width. When the cursor y position is greater than the window height 3812, the y position is set 3814 to zero. When the cursor y position is less than zero 3816, the y position is set to the window height 3818. Once the cursor x and y values are adjusted, the cursor is displayed.

The zoom operation starts with the user initiating 3902 the zoom tool as depicted in FIG. 39. The system checks 3904 to see if the mode is the zoom point mode. If not the existing pivot point (the sphere) is displayed 3906. If in the point mode, a check 3908 on whether the cursor is over the model is performed. If so, the point is determined 3910 and displayed 3912. If the cursor is not over the model, the intersection point based on the alternate metric is displayed 3914, such as setting the point a predetermined distance into the space from the current camera position or view point as previously described. When the user moves 3914 the cursor, the camera or view is moved 3916 along the vector (in or out depending on the cursor motion) from the cursor to the pivot point. The motion of the camera is adjusted 3918 based on maximum limits and whether the pivot point has been encountered. When the mouse button is released 3920, motion stops.

During tool operation, the rewind history is saved and this operation 4002 is shown in FIG. 40. The system checks 4004 to see if this tool requires intermediate waypoints and, if so, the elapsed time since the last waypoint was saved is checked 4006 against the waypoint interval. If it is time to add a waypoint, the current view state information is added 4008 to the rewind history and a thumbnail is created. When the tool does not require period waypoints, the system waits for the current tool operation to end 4010 and then saves 4012 a new waypoint.

FIG. 40a illustrates a linked list data structure used for the movement history where each entry 4020 includes view location, orientation, etc.

FIG. 41 shows the flow of the rewind tool operation. When the rewind tool is activated 4102, the hold down period of the tool is compared 4104 to a threshold and if it is less than the threshold, the system moves or animates 4106 the view back one step (or back to the place where the last thumbnail was saved). When the user moves 4108 the rewind cursor 712 (see FIG. 7), the view is updated or animated 4110, preferably linearly based on the thumbnails involved in the motion of the rewind cursor as previously discussed. While the mouse button is down 4112, the motion can continue.

During operation of the forward tool, when the user presses 4202 the mouse button, the system determines 4204 whether the cursor is over the model as depicted in FIG. 42 and if not the invalid operation cursor and message is displayed 4206. Otherwise, the intersection point is determined 4208 and displayed 4210 along with the motion scale (see FIG. 27), followed by a move 4212 of the view a predetermined distance to the intersection point, such as preferably 50%. The scale is updated to show the amount of movement. If the cursor is moved up 4214, the movement percentage is increased 4216. If the cursor is moved down 4218, the percentage is decreased 4220. When the mouse button is released 4222, the movement percentage is used to move both the view and the marker on the perspective scale.

The up/down tool flow is activated 4302 and when the user moves 4304 the cursor, the camera view is moved 4306 along the up vector (a vector vertical with respect to the model) based on the current position as shown in FIG. 43. The camera position is adjusted 4308 based on the minimum and maximum positions. The up/down scale is updated and displayed to show the move. This continues as long as the mouse button is down 4310.

As shown in FIG. 44, the walk tool, when activated 4402, the system warps 4404 the cursor to the starting position as previously discussed. When the cursor is inside the start region 4406, the speed is set 4408 to zero. When the cursor is above the start region 4410, the view is moved forward based on a speed that is increased 4412 responsive to the distance the cursor is above the start region. When the cursor is below the start region 4414, the view is moved based on a speed that is decreased 4416 responsive to the distance the cursor is below the start region. When the cursor is to the right of the start region 4418, the view is rotated right 440 based on the distance the cursor is to the right of the start region. When the cursor is to the left of the start region 4422, the view is rotated left 4424 based on the distance the cursor is to the left of the start region.

The pan operation (see FIG. 45), when activated 4502 by clicking through the pan tool, determines 4504 whether the cursor is over the model. If so, the intersection point is determined 4506 and a C:D ratio (the rate of movement speed) is set 4508 based on the distance to the intersection point and the scene is panned based on the motion of the cursor using the ratio. If not over the cursor, the C:D ratio is set 4510 based on an alternate metric, such as the dimensions or size of the model space and the scene is panned responsive to cursor motion.

The mini-wheel activation (see FIG. 46), when activated 4602 by clicking through the pan tool, determines 4604 whether the cursor is within the wheel boundary. If not, the position of the wheel is updated 4606. If so, a determination 4608 is made as to whether the cursor is in the highlighted wedge. If not, a determination is made 4610 as to whether it is within the specified distance of the wedge. If not, the wedge is highlighted 4612.

Perspective and orthographic projections differ in that orthographic projection has no sense of depth. Thus, when using only a view direction to determine the perspective and orthographic frustums for a scene, a great disparity can emerge between the two after several camera operations have been carried out. Depicted in FIG. 47 is an approach 4700 to maintaining parity between perspective and orthographic projections, by using a single camera model, from which both orthographic and perspective viewing frustums can be derived.

The standard pinhole perspective camera model has been augmented to include the distance to the geometry in the scene. This is updated whenever the camera position changes. That is, the user performs a camera move operation 4702, the camera parameters are updated 4704 and the distance to the object is updated 4706. We then use this extra information to scale the orthographic frustum such that the size of the geometry as it is viewed in orthographic projection mimics the size of the geometry as it is viewed in perspective projection. In doing this, a determination 4708 is made as to whether the mode is projection or perspective. If perspective, the perspective frustum is calculated 4710. If orthographic, the distance is used to calculate 4712 the frustum. After the frustum is determined, the view is rendered 4714.

This distance value is used when calculating 4712 the orthographic frustum; the parameters of orthographic width and height are calculated from the pinhole camera model as follows: ORTHO_(w) =d×tan(f _(hor)) ORTHO_(H) =d×tan(f _(ver)) where d is the distance to the geometry in the scene, and f_(hor) and f_(ver) are the horizontal and vertical field-of-views, respectively.

The approximate distance to the object can be calculated based on the distance of the perspective camera's eye to the center point. In doing this the position of the center point is updated throughout all camera operations and generally lies on scene geometry. This is an effective and computationally inexpensive way of approximating distance to the geometry in the scene. In addition, the magnitude of the view direction vector is transparent to the perspective projection model. However, as this is an approximation, it does not work in all cases.

Another approach is to calculate the actual distance to the geometry view for every frame. While this ensures the calculation of the orthographic frustum is accurate, it is computationally expensive. Carrying out such calculations on a graphics processing unit (GPU) helps reduce the load on a central processing unit (CPU) but can result in slower than real-time interaction for complex geometry.

The typical hardware 4800 for the system discussed herein, as depicted in FIG. 48, includes a display 4802 that can be a non sensitive display or a sensitive display such as a touch or stylus type display screen as used in tablet or lap top type computers. The display is coupled to a computer 4804 that can have the power of a cell phone, PDA, lap top, desk top or server type computer. A keyboard 4806 is provided for the key based operations. A mouse 4608 or other cursor position control input device is used to control the cursors discussed herein. A digitizing tablet 4810 that uses a stylus 4812 can also be coupled to the computer. Other types on input devices that allow selection and cursor motion can also be used. The computer has associated memory and other types of storage capability (CD, hard disk, DVD, etc.) to allow the programs or processes and data structures discussed herein to be stored. The system can operate over a network as the need arise for more power or speed with the processes, etc. being distributed.

The embodiments of the present invention discussed provide a safe 3D navigation environment by clustering and caching tools; creating task and skill-based tool sets; providing orientation awareness; enhancing tool feedback; providing pre-canned navigation; preventing errors; and recovering from errors. Rapid access and use are provided by the tracking menu and click through features. The circular design of the wheels with important action tools on the exterior and less used tools in the interior organizes the tools so they are easy to access in an order that fits the tasks. The tool selection dialogs that allows new and advanced users to select a navigation tool makes the users quickly aware of what is available and what are the navigation tool uses and allows immediate selection. The task grouping of commonly used tools for and limited to types of tasks helps prevent users from becoming confused during navigation. The customization of the action tools for the type of task also prevents confusion and errors during navigation. The sphere provides visual feedback to orient the users and the limitations on placement of the sphere prevent navigation errors. The sliders provide location feedback for dragging operations. Labels and icons reinforce the operations of the tools being used. Constraints on navigation, such as limiting motion to the bounding box or to a rear wall along with cursor control like the cursor screen wrapping, keeps users from getting into visually confusing states. Error recovery using rewind allows users to return to a familiar visual state.

When any of the 3D wheels are selected, and the user then navigates to a 2D sheet, the 2D navigation wheel can automatically become the selected tool. When the 2D navigation tool is selected tool and the user navigates to a 3D model, the last used 3D Wheel will become the selected tool. If the ‘pinned’ option is enabled, show the 3D wheel pinned to the canvas. If a non-compatible section type is displayed in the canvas the wheel(s) are dismissed and the Select Tool is activated instead.

Depending on the hotkey being used, it may be preferable to offer spring-loaded activation of the wheel. That is, only when the hotkey is pressed down, the wheel is visible and a user can interact with it. Once the hotkey is released, the wheel goes away. Again, this is an optional offering depending on the available hotkey and ease of articulation.

Alternative, and less ideal, systems may be built that offer the collection and sets of navigation tools not using the Tracking Menu design but instead using standard tools on a toolbar as well as potentially offering hotkey access to the individual tools. So, for example, a 3D navigation tool palette may offer: Forward, Look, Rewind, and Up/Down tools as one set and Center, Zoom, Rewind and Orbit as another set.

Additionally, the shapes of the Tracking Menus may be altered (from circles to other shapes such as ovals or squares) and the tool regions shapes may be reshaped and their proportions changed. The positioning of the tools may also be rearranged (e.g., the Orbit wedge on the left side of the wheel could be moved to the top wedge).

Other elements such as the “green ball” may be different colors or shapes (e.g., square or pyramid or cross), orientation demarcations (e.g., tick marks instead of axis belts) and have different transparency dynamics.

Note also that the help text in the HUDs and tooltips change based on the language settings of the computer (e.g., French, Chinese, etc).

The Rewind tool can have different visual representations for each waypoint and be presented to the user in different styles (such as a line with beads on it or timestamps, or a stack of thumbnails or a stack of graphical objects) and different orientations (e.g., vertical instead of horizontal or in 3D). The Rewind mechanism can be attached to different input devices such as the mouse scrollwheel. Additional information can be saved in the Rewind queue beyond camera position and orientation such as user settings, background color and styles, environment settings, rendering modes (e.g., line or shaded), camera options such as orthographic or perspective projection, etc. When Rewinding occurs, the previous state information is installed. In some cases, interpolation of application state information can occur between two waypoints. For example, if the user switched between perspective and orthographic projection, these two projection modes would be blended when rewinding between the two waypoint events.

In addition to the thumbnail strip, supplementary information can be presented such as user or system annotations or indicating which tools were active during the navigation history or other system activity. The Rewind thumbnail strip and graphics may be drawn semi-transparently.

Note for the Rewind Tool, it is possible to save the exact movement path the user performed (instead of just the last position and orientation when the mouse is released). We call this “high resolution”. We have found that this is mostly undesired and requires a lot of information to be saved. However, we prototyped this and found it too frenzied when someone dragged through the rewind history. Nevertheless, it may be useful in some applications in which a modifier key can be hit to toggle between using low or high resolution rewind information.

Also navigation events may be created by the system (not explicitly by the user). These can be added to the Rewind history.

Note that some events may be compressed or combined. For example, navigation events that occurred in which the view did not change or in which the view was composed of viewing empty space, are candidates for being dropped from the Rewind history or compressed into a single event.

The perspective sliders can be used in other contexts where for example 3D depth information is useful to indicate. Note that an interesting property of the perspective slider is that it can take less visual space than a 2D slider since it is drawn in perspective.

The perspective slider does not have to relate to positional information about the 3D scene. For example, it can adjust volume settings. The point is that it is drawn in perspective and the perspective may not even match the current perspective in the 3D scene. Also, it could be used in a 2D canvas or 2D application.

The slider can be drawn such that it become more transparent as the slider is deeper in the scene. Thus, the “Start” end of the slider would be more opaque and the “Surface” end would be more transparent.

The perspective slider can be drawn in many different visual ways using different metaphors such as a measurement ruler, or a road/driveway.

User or system annotation labels (text, graphics, iconic symbols) can be added on or near the slider to provide information and context.

Additional semantic controls to go up one floor or down one floor—or other units (e.g. one meter, one foot, etc.), instead of up/down one page or screen full of information on typical scrollbars.

Input snapping at interesting points along the slider (e.g., at each floor or tick mark indicating distance) may also be added for additional user control.

The up/down slider may also have additional graphics, annotations and tick marks on it to indicate application specific information or sizing/scale information. For example, tick marks may indicate floors in a building or where important elements are in a building (such as pipes, electrical junctions, etc. Drag snapping can occur at designated points along the slider for precise movement. In some cases, it may be useful to enable the tool without drawing the graphical slider. The slider may also be drawn semi-transparently. The preferred behavior is for the slider to initially appear near the current cursor position but it may be useful to have it come up in other locations such as the center of the 3D canvas.

Pre and Post actions may be conducted while using the slider. For example, temporarily leveling the camera such that it is parallel to the ground plane before and after actions are performed while using the Up/Down slider.

During mouse-dragging input for the Up/Down tool, the mouse movement can be mapped to a non-linear function to move the camera. For example, an exponential function (which we use), has the property that initial mouse movement move the view in small amounts (for precise adjustments) and as the drag motion gets longer, large view movements are generated. This design is handy if the user is viewing a condominium building and wants to either move up/down in small distances (e.g., within a floor) or large distances (multiple floors at a time).

The Walk tool may deploy intelligent sensing to automatically determine a constant height above the current “ground plane” or horizontal surface the camera is currently over. Smoothing algorithms would make the transition to different heights more visually pleasing. Additional sensing could be used to avoid objects or walls. In addition note that application specific or user customized HUD messages and graphic annotations can be triggered and displayed depending on the user's current location, direction and speed of travel. Moreover to ensure smooth traveling, the system may deploy “level of detail” adjustments in the graphics rendering of the scene—drawing fewer polygons and performing less rendering in dense scenes to approximate the visuals to keep the refresh redrawing at a high rate. Hotkeys may be used to increase or decrease the speed factor of the walk movement.

It is possible to have the walk left/right action and the up/down action be assigned to different parameters (e.g., navigation directions). For example, left/right may pan the user left/right instead of the default look left/right. It is also possible to have the up/down mouse direction map in the up/down direction instead of the in/out direction. Thus, a rate-based pan operation which behaves directionally similar to the standard Pan operation but is rate based.

As a convenience, if the user is walking using the Walk tool and performs cursor-wrapping, moving the cursor into the dead zone will cause the movement to stop and reset the speed to zero. Thus, the user does not have to disengage the Walk tool (by releasing the mouse), or “unwrap” the cursor to pause and reset movement.

The method of cursor-wrapping can be activated while the user input is in the tracking state (e.g., moving a mouse device with no buttons pressed) or during a drag state (e.g. moving a mouse device with the left mouse button pressed). In most scenarios, the cursor-wrapping is active when a tool is active (such as dragging while orbiting).

With cursor-wrapping, the concepts are the same for a view displaying a mixture of 2D and 3D or purely 2D content. When the cursor reaches the out-of-view position, an audio signal or visual signal can be displayed near the cursor location. For example, a chirp sound may be heard and the cursor could fade out, then fade in on the other side. Alternatively, as an example, a small animation could be played showing a puff of smoke near the cursor location. Note that it is possible to display a portion of the cursor (and auxiliary graphics that are currently moving with the cursor—such as a tool/cursor label or status information) at the out-of-view position and the remaining portion at the new wrapped-around position. A number of variations are possible: clip the cursor and auxiliary graphics; re-format or reposition the auxiliary graphics to remain visible until the cursor completes its wrap; always keep the cursor displayed whole but allow auxiliary graphics to be split.

The cursor-wrapping boundary may be dynamically defined to be not the current view boundary but the boundary of the currently selected object or set of objects in the scene. In addition, the cursor-wrapping boundary could be dynamically determined to be the bounds of the object it currently is over. Both of these cases are useful in that it keeps the cursor near where the user is working and auxiliary information that is moving with the cursor (such as dimensioning, status info, or state information) can remain nearby.

For the Tap Activation functionality, some embodiments will only implement the quick tap toggle to activate/deactivate a tool and not the spring-loaded tap to activate a tool. In the quick tap situation, the trigger will often require that “no mouse buttons are pressed” as this is typically reserved for modifying the current selection.

If spring-loaded mode is supported, then mouse button presses are processed. However, the trigger key is already in use so if the tool requires this key, it is unavailable. That is why we like less used combinations such as cntrl+shift or the Alt key. The First Contact pop-up mechanism is anchored to some visual element (e.g., a tool icon button in a toolbar or a widget in the 2D/3D scene). In our case we put a grayed-out 2D graphic on top of the 3D scene.

An important behavioral design to capture is that the FirstContact graphic will dismiss itself when the user moves the cursor outside of the bounds of the graphic. Moving the cursor over sub-elements of the graphic may change the graphic and switch default settings for the tool if the user chooses to activate the tool by clicking with the mouse. Thus, the user customizes the tool while learning about the tool or collection of tools.

It is important to emphasize that the user can switch between options by clicking on sub-element graphics without activating the tool. These graphics are used to select different sub-groups. We have found that an important grouping is by user expertise. Moreover, users are very bad at self-assessment and classifying themselves as a novice or expert. Thus, we strategically do not use these terms and instead use terms such as “Familiar with 3D” and “New to 3D”.

One style of FirstContact is that the FirstContact graphics and tool choosing should be seen only until the user activates the tool for the first time. This is to reduce information overload and clutter. The next time the user hovers over the anchor element, the FirstContact will not be presented. This state information is preserved in the user preferences and thus when the application is re-launched, FirstContact exposure is respected.

A mechanism exists to always re-activate FirstContact on application start-up for those users who want this mechanism to persist and to always be shown FirstContact.

The “green ball” navigation sphere has some important characteristics. The sphere becomes more transparent as the user gets closer during a camera movement operation (such as zoom) until the sphere is completely transparent.

Also it is important to note that the size of the sphere resets after any camera movement operation. When the sphere is interactively moved within the 3D scene, its size changes depending on the depth location information. By default, the sphere does not cast a 3D shadow but it could if desired. A texture could be added to the sphere to alter its appearance.

We display the focus point sphere on tool activation (i.e., mouse down) and remove it on tool deactivation.

Alternatively, one may choose to show/hide the sphere when the tool is selected from the toolbar—in addition to when the tool is being used (e.g., while the mouse button is pressed). The sphere could change color when the tool is being used (i.e., mouse down).

The sphere could change shape, color or be annotated with graphics or icons to indicate state or mode information. For example, within the Orbit tool, the sphere could indicate if dimensional constraints were active (e.g., only allowing orbit in x dimension).

In general modifier keys can be used for all of the tools to add additional functionality.

The many features and advantages of the embodiments are apparent from the detailed specification and, thus, it is intended by the appended claims to cover all such features and advantages of the embodiments that fall within the true spirit and scope thereof. Further, since numerous modifications and changes will readily occur to those skilled in the art, it is not desired to limit the inventive embodiments to the exact construction and operation illustrated and described, and accordingly all suitable modifications and equivalents may be resorted to, falling within the scope thereof. 

What is claimed is:
 1. A method, comprising: detecting activation of a trigger key; and determining whether to one of activate, deactivate, and keep active a tool responsive to activation of the trigger key by detecting a status of the tool upon the activation of the trigger key, wherein determining comprises: determining whether the tool is currently active; upon determining that the tool is currently active: detecting release of the trigger key; comparing a key hold down time to a threshold after determining that the tool is currently active; keeping the tool active when the hold down time is greater than the threshold; and deactivating the tool when the hold down time is not greater than the threshold, and, upon deactivating the tool, automatically activating a previously used tool; after detecting that the trigger key has been released, detecting that a second trigger key has been activated; and keeping the tool active while the second trigger key remains activated.
 2. A method as recited in claim 1, wherein the determining is while no mouse buttons are activated.
 3. A method as recited in claim 1, wherein the trigger key is one of cntrl+shift and Alt.
 4. A method as recited in claim 1, further comprising activating a tool selection menu when an active tool is deactivated.
 5. An apparatus, comprising: a display; and a computer for: detecting activation of a trigger key; and determining whether to one of activate, deactivate, and keep active a tool responsive to trigger key activation by detecting a status of the tool upon the activation of the trigger key, wherein determining comprises: determining whether the tool is currently active; upon determining that the tool is currently active: detecting release of the trigger key; comparing a key hold down time to a threshold after determining that the tool is currently active; keeping the tool active when the hold down time is greater than the threshold; and deactivating the tool when the hold down time is not greater than the threshold, and, upon deactivating the tool, automatically activating a previously used tool; after detecting that the trigger key has been released, detecting that a second trigger key has been activated; and keeping the tool active while the second trigger key remains activated.
 6. A non-transitory computer readable storage having a program for controlling a computer apparatus to execute an operation, comprising; detecting activation of a trigger key; and determining whether to one of activate, deactivate, and keep active a tool responsive to trigger key activation by detecting a status of the tool upon the activation of the trigger key, wherein determining comprises: determining whether the tool is currently active; upon determining that the tool is currently active: detecting release of the trigger key; comparing a key hold down time to a threshold after determining that the tool is currently active; keeping the tool active when the hold down time is greater than the threshold; and deactivating the tool when the hold down time is not greater than the threshold, and upon deactivating the tool, automatically activating a previously used tool; after detecting that the trigger key has been released, detecting that a second trigger key has been activated; and keeping the tool active while the second trigger key remains activated.
 7. An apparatus, comprising: a display; and a computer for: displaying a tool selection menu for selecting a plurality of tools; detecting activation of a first trigger key; and determining whether to one of activate, deactivate, and keep active a first tool in the plurality of tools by detecting a status of the first tool upon the activation of the first trigger key, wherein determining comprises: upon determining that the first tool is currently active: detecting release of the first trigger key; comparing a key hold down time to a threshold after determining that the first tool is currently active; keeping the first tool active when the hold down time is greater than the threshold; and deactivating the first tool when the hold down time is not greater than the threshold; detecting activation of a second trigger key; while the second trigger key remains active: activating the first tool and keeping the first tool active; and displaying a cursor and not displaying the tool selection menu; and upon detecting release of the second trigger key: deactivating the first tool; and displaying the tool selection menu.
 8. A method as recited in claim 1, further comprising: upon determining that the tool is not currently active: activating the tool; detecting release of the trigger key; comparing a key hold down time to a threshold; keeping the tool active when the hold down time is not greater than the threshold; and deactivating the active tool when the hold down time is greater than the threshold, and upon deactivating the tool, automatically activating a previously used tool.
 9. The apparatus as recited in claim 5, wherein the computer is further for: upon determining that the tool is not currently active: activating the tool; detecting release of the trigger key; comparing a key hold down time to a threshold; keeping the tool active when the hold down time is not greater than the threshold; and deactivating the active tool when the hold down time is greater than the threshold, and upon deactivating the tool, automatically activating a previously used tool.
 10. The non-transitory computer readable storage as recited in claim 6, wherein the operation further comprises; upon determining that the tool is not currently active: activating the tool; detecting release of the trigger key; comparing a key hold down time to a threshold; keeping the tool active when the hold down time is not greater than the threshold; and deactivating the active tool when the hold down time is greater than the threshold, and upon deactivating the tool, automatically activating a previously used tool. 